Problem Note 58174: SAS® Deployment Manager might not restart after you click Yes in prompt to apply a SAS Private Java Runtime Environment hot fix to SAS® 9.4 (TS1M3)
When you apply a SAS Private Java Runtime Environment hot fix to an existing SAS 9.4 (TS1M3) installation, Rev. 940_15w38 and later, you are prompted with a message stating that SAS Deployment Manager needs to restart. When you click Yes to restart the SAS Deployment Manager, it does not restart. No error is displayed.
Messages Appear in Your Logs
When this problem occurs, messages similar to the following appear in your logs.
In SDM_<date_time>.log:
Mar 14, 2017 3:20:41 PM com.sas.ssn.StagedSDM copySasdm
INFO: Copying sasdm launcher for staged SAS Deployment Manager: source: C:\Program Files\SASHome\SASDeploymentManager\9.4\product_data\deploywiz__94390__prt__xx__sp0__1\..\..\sasdm.exe destination: C:\Program Files\SASHome\InstallMisc\SASDeploymentManager\sasdm.exe
Mar 14, 2017 3:20:41 PM com.sas.ssn.Kit exitKit
INFO: Exit Code = 16000
In sasdm_<date_time>.log:
Tue Mar 14 15:20:41 2017
INFO: ExeProc::ExeandDisplay::GetExitCodeProcess=16000
Tue Mar 14 15:20:41 2017
INFO: CWinlauncherApp::InitInstance=16000
Tue Mar 14 15:20:41 2017
INFO: CWinlauncherApp::CleanupScript does not exist=
Tue Mar 14 15:20:41 2017
INFO: CWinlauncherApp::SASHome=
Tue Mar 14 15:20:41 2017
INFO: CWinlauncherApp::altlauncherScript=\InstallMisc\SASDeploymentManager\sasdm.exe -cleandir "\InstallMisc\SASDeploymentManager"
Tue Mar 14 15:20:41 2017
ERROR: ExeProc::ExeandWait::CreateProcess=2
Tue Mar 14 15:20:41 2017
INFO: CWinlauncherApp::ExitInstance=-1
Workaround
- Navigate to C:\Program Files\SASHome\InstallMisc\SASDeploymentManager\.
- Right-click the sasdm.exe executable and select Run As Administrator. This selection invokes the SAS Deployment Manager, and the installation of the hot fix completes.
Operating System and Release Information
SAS System | SAS Deployment Manager | Microsoft® Windows® for x64 | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8 Enterprise 32-bit | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8 Enterprise x64 | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8 Pro 32-bit | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8 Pro x64 | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8.1 Enterprise 32-bit | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8.1 Enterprise x64 | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8.1 Pro 32-bit | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows 8.1 Pro x64 | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2008 | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2008 R2 | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2008 for x64 | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2012 Datacenter | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2012 R2 Datacenter | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2012 R2 Std | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Microsoft Windows Server 2012 Std | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Enterprise 32 bit | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Enterprise x64 | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Home Premium 32 bit | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Home Premium x64 | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Professional 32 bit | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Professional x64 | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Ultimate 32 bit | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
Windows 7 Ultimate x64 | 9.49508 | 9.49546 | 9.4 TS1M3 | 9.4 TS1M4 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
Type: | Problem Note |
Priority: | medium |
Date Modified: | 2017-03-27 12:00:08 |
Date Created: | 2016-05-05 15:15:38 |